Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Configuring OpenEdge DataServer for MS SQL Server

This section provides an example of setting up the connection with the OpenEdge DataServer for MS SQL Server. You must supply the following connection parameters when you set up the connection to the schema holder database:

-db Progress_schema_holder_name -H host -S service -N TCP -db ODBC_DSN_name -ld SQL_Server_db -dt MSS -U user_name -P password -H broker_host -S broker_service -Dsrv TXN_ISOLATION,1

You first supply the startup parameters for the schema holder database (Progress_schema_holder_name, etc.). The remaining parameters are used to start the DataServer connection to the non-OpenEdge database (ODBC_DSN_name, etc.).

The following example shows how this information is stored in the icfconfig.xml configuration file:

<service> <cServiceType>Database</cServiceType> <cServiceName>MSS</cServiceName> <cPhysicalService>MSSn</cPhysicalService> <cConnectParams>-db sh_mydb -N TCP -H localhost -S demo_svc -db mss_dsn_db     -ld mss_db -dt MSS -U icftest -P icftest -Dsrv TXN_ISOLATION,1 </cConnectParams> <lDefaultService>no</lDefaultService> <lCanRunLocal>yes</lCanRunLocal> <iStartOrder>0</iStartOrder> </service>

Some important points:

For Microsoft SQL Server, the database type is always MSS.
The DSN name is the configured DSN that you use to access the MS SQL Server database with ODBC. It does not need to be the same name as the SQL Server database. When the DSN is configured, the name of the physical MS SQL Server database is specified.
The logical name for the database is the name that you use to access the MS SQL Server database with the 4GL. If a logical name is not specified, the default logical name is used. This is the name of the DSN for MS SQL Server.
The isolation level is set to one using -Dsrv TXN_ISOLATION,1. This provides OpenEdge-like locking using MS SQL Server’s read uncommitted transaction isolation level.
The -ld and -dt parameters are optional.
If the schema holder is on the same machine as the client, then the -H and -S parameters for the schema holder are optional.
Because this example is for a system using the Personal version of the MS SQL Server DataServer, the -H and -S parameters are not specified for the database broker. If your system uses the enterprise version, the -H and -S parameters are needed if the database broker is located on a machine other than the client. The "Configuring OpenEdge DataServer for Oracle" section provides an example of using these parameters.